Skip to content

Conversation

@wangye805
Copy link
Collaborator

In case when NVTE_FUSED_ATTN_ is set during building

Description

Please include a brief summary of the changes, relevant motivation and context.

Fixes # (issue)

Type of change

  • Documentation change (change only to the documentation, either a fix or a new content)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Infra/Build change
  • Code refractor

Changes

Please list the changes introduced in this PR:

  • Change A
  • Change B

Checklist:

  • I have read and followed the contributing guidelines
  • The functionality is complete
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

In case when NVTE_FUSED_ATTN_<backend> is set during building
@wenchenvincent
Copy link
Collaborator

@wangye805 Do we still need this PR?

@wangye805
Copy link
Collaborator Author

@wangye805 Do we still need this PR?

Probably not needed with Ilya's PR #167. I'll double check and close if not needed.

@wenchenvincent
Copy link
Collaborator

@wangye805 Is this PR still needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants